Method and system for preventing illicit use of a telephony platform

ABSTRACT

A system and method for preventing illicit use of a telephony platform that includes enrolling a plurality of accounts on a telecommunications platform, wherein an account includes account configuration; at a fraud detection system of the telecommunications platform, receiving account usage data, wherein the usage data includes at least communication configuration data and billing configuration data of account configuration and further includes communication history of the plurality of accounts; calculating fraud scores of a set of fraud rules from the usage data, wherein at least a sub-set of the fraud rules include conditions of usage data patterns between at least two accounts; detecting when the fraud scores of an account satisfy a fraud threshold; and initiating an action response when a fraud score satisfies the fraud threshold.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 61/675,156, filed on 24 Jul. 2012, which is incorporated in itsentirety by this reference.

TECHNICAL FIELD

This invention relates generally to the telephony field, and morespecifically to a new and useful method and system for preventingillicit use of a telephony platform in the telephony field.

BACKGROUND

Telephone fraud has long been a problem for telephony systems. With theintroduction of VoIP networks and Session Initiation Protocol (SIP)trunks, the opportunities for telephony fraud is even greater. Therecent development of new telephony platforms that enable a wider rangeof developers to create useful products also enables nefarious partiesto create programs that commit telephony fraud. As one example, tollfraud has become a common problem on telephony platforms due in part toeasier access to disposable telephone numbers. Other forms of telephonyfraud can result in chargebacks for telephony platform providers whenthe telephony fraud involves stolen credit cards. Yet other forms oftelephony fraud use valuable resources for improper uses that wouldotherwise be used for legitimate applications. Telephony fraud can bedamaging to users that fall victim to the telephony frauds, to theprofitability of telephony platforms, and to the performance oflegitimate telephony applications. Furthermore, as developers are morefrequently building on top of other infrastructure, those developers maynot have access to the raw information to prevent such illicit use oftheir applications. Thus, there is a need in the telephony field tocreate a new and useful method and system for preventing illicit use ofa telephony platform. This invention provides such a new and usefulmethod and system.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic representation of a system of a preferredembodiment of the invention;

FIG. 2 is a flowchart representation of a preferred embodiment of theinvention;

FIG. 3 is a schematic representation of a preferred embodiment of theinvention;

FIG. 4 is a schematic representation of a preferred embodiment of theinvention for integrating a fraud scoring system with a data stream;

FIG. 5 is a flowchart depicting a variation of a preferred embodiment ofthe invention for updating received usage data upon receiving a triggersignal;

FIG. 6 is a flowchart depicting a variation of a preferred embodiment ofthe invention for calculating a fraud score from usage data associatedwith call history data;

FIG. 7 is a flowchart depicting a variation of a preferred embodiment ofthe invention for calculating a fraud score from usage data associatedwith message history data;

FIG. 8 is a flowchart depicting a variation of a preferred embodiment ofthe invention for calculating a fraud score from usage data associatedwith platform account data;

FIG. 9 is a table depicting a fraud rule set of an exemplaryimplementation of a preferred embodiment of the invention; and

FIG. 10 is a flowchart depicting a variation of a preferred embodimentof the invention for generating a fraud rule.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of the preferred embodiments of the inventionis not intended to limit the invention to these preferred embodiments,but rather to enable any person skilled in the art to make and use thisinvention.

1. System for Preventing Illicit Use of a Communication Platform

As shown in FIG. 1, a system for preventing illicit use of acommunication platform of a preferred embodiment can include acommunication platform 100 that includes a multitenant account system110 and a fraud scoring system 120 communicatively coupled tooperational components 130 of the communication platform. The systemfunctions to apply various fraud-based heuristics across the accountsand/or subaccounts of the platform 100, monitor and measure the scoresbased on the heuristics, and alter operation of the account within thecommunication platform. Such a system is preferably capable ofmitigating fraudulent behavior made on top of a self sign-upcommunication platform. In one scenario, the system can be applied topreventing illicit use within a single account. The system canadditionally be extended to detect illicit use through cooperative useof multiple accounts. Another aspect is that the multitenant accountsystem may include functionally for an account to create sub-accounts.Sub-accounts can be used so that a developer can develop a service ontop of the communication platform and provide that service to endcustomers. The system can enable fraudulent behavior within thesubaccount of an account to also be monitored for fraudulent behavior.

The communication platform 100 functions as the main infrastructure onwhich fraud is sought to be prevented or reduced. The communicationplatform is more preferably a telecommunication platform thatfacilitates synchronous voice communication sessions, synchronous videocommunication sessions, screen-sharing session, asynchronous text ormedia communication. In particular traditional telecommunicationprotocols such as telephone based networks (e.g., PSTN) or carrier basedmessaging (e.g., SMS or MMS) are of particular attention in theprevention of fraud. The ecosystem of traditional telecommunicationprotocols includes user contracts and network/carrier contracts tofacilitate interoperability and functioning of the communication networkas a whole. The communication platform 100 in some variations mayprovide a way for account holders to avoid the various contract relatedrestrictions usually involved in using the network. For example, anaccount may be created and used through self sign-up, avoiding acontract lock-in or enrollment process. As described below accounts canadditionally acquire and drop communication endpoints on-demand. Thefraud scoring system preferably functions to ensure that such beneficialfeatures are not leveraged in implementing toll fraud, spammingtechniques, scams, or other illicit uses of the communication platform100.

The communication platform 100 can provide any suitable service. In onevariation, the communication platform 100 provides routingfunctionality. In another variation, the communication platform 100 mayprovide communication bridging between at least two protocols such as aPSTN device talking to a SIP based device. In a preferred embodiment,the communication platform 100 provides communication applicationfunctionality and/or API based integration to communication sessions,events, and resources. The communication platform preferably enablesaccounts to configure applications to be responsive to incomingcommunications. The communication platform 100 can additionallyfacilitate initiating outbound communications to be controlled by anapplication or connected to an agent. The applications are preferablyinternet hosted telephony instruction documents hosted externally by thedevelopers (e.g., the account holder). The applications are preferablyconfigured as URI mappings within an account that relate an endpointwith an application URI. The URI based applications preferably enableweb developers to easily apply web-based application skills to buildingdynamic telephony applications. The communication application platformis preferably substantially similar to the one described in U.S. Pat.No. 8,306,021, issued 6 Nov. 2012, which is hereby incorporated in itsentirety by this reference. The communication platform 100 mayalternatively be focused on providing some features directed at atargeted use case. For example, the communication platform 100 may be acustomer service platform used by customers to build call centers. Thecommunication platform 100 may be a conference call service, a personalvoicemail system, a notification service, a two-factor authenticationfacilitating service, and/or any suitable type of communicationplatform.

The multitenant account system 110 functions to manage and facilitatethe accounts within the communication platform 100. As described above,the communication platform 100 is preferably a multitenantinfrastructure in that multiple users can independently operate onshared resources of the communication platform. Preferably, any givenaccount is prevented from impacting the resources of others within amultitenant system. The account system no preferably includes a userinterfaced and/or programming interface (API) to create and manage anaccount. The communication platform will often involve paid use ofcommunication infrastructure. The account system may include a billingengine that stores payment information of the account. Within anindividual account, at least one endpoint is preferably assigned as acommunication address. The communication endpoint is preferably a phonenumber, but may alternatively be a SIP address, a user name, or anycommunication address. The account system 110 or an endpoint service mayadditionally facilitate an account from acquiring new endpoints, portingoutside endpoints for use within the platform, and/or cancelingendpoints. The account system 110 can additionally manage operationalconfiguration such as storing resources, references to resources,parameter settings, or other aspects used in account usage of thecommunication platform 100. Preferably, the configuration can store theapplication URIs mapped to endpoints of the account.

Additionally, the multitenant account system no can include asub-account system such that a hierarchy of accounts can be created. Afirst account (i.e., a parent account) can preferably create or containmultiple sub-accounts (i.e., children accounts). Sub-accounts may becreated through an interface by the sub-account holder or alternativelythrough an API by the parent account holder. For example, an applicationdeveloper may create a customer service application, and then allow endusers to signup as customers within his account. The sub-accounts willpreferably operate within the scope of the parent account. Thesub-accounts can be customized by the parent account and/or customizedby sub-account holder. In one implementation, the sub-account system mayfunctions similarly to the system and method described in U.S. patentapplication Ser. No. 13/167,569, filed 23 Jun. 2011, which is herebyincorporated in its entirety by this reference.

The fraud scoring system 120 functions to monitor, measure, and detectinstances of illicit use that occur within or through the communicationplatform. The fraud scoring system 120 may predominantly focus onpreventing continued illicit use of the communication platform 100 thatis initiated by an account and/or a parent account of the communicationplatform 100. The fraud scoring system 120 can additionally identify andprevent illicit actions initiated by parties outside of the platform butoccurring through the communication platform 100.

The fraud score preferably includes a set of fraud rules. The fraudrules are preferably conditions that either act as a metric upon which ascore is based. The scores of the various fraud rules are preferablycollectively analyzed to determine if fraud is occurring. A fraud rulein one variation is used in calculating a scalar measurement of onedimension or indicator of fraud. A fraud rule may alternatively be setof discrete conditions with an assigned score based on the determinedcondition. Preferably, this will be binary decision of assigning a fraudscore or not. The fraud rules can target various aspects ofcommunication and account usage and configuration. The fraud rules maysimply evaluate indicators of fraud within an account or sub-account.Additionally, the fraud rules may include analysis acrossaccounts/sub-accounts to detect patterns of illicit use implementedusing multiple accounts. The fraud rules may be preconfigured orautomatically generated based on algorithmically learned patterns infraud or anomaly detection. The fraud scoring system no may additionallyinclude an analyst-facilitated user interface wherein new rules can becreated and issues can be manually ignored or acted upon, whichfunctions to supplement automatic operation with human insight.

The set of fraud scores can include a wide variety of rules that use avariety of data sources. The data sources may include communicationhistory such as involved endpoints, duration of the communication,content of the communication, frequency of the communications,geographic information of the communication, and other loggedinformation. Some of the conditions may be based on static configurationparameters (i.e., how the account is setup). If an entity isimplementing illicit behavior across multiple accounts similar resourcesare preferably used, and thus similarities of account settings acrossmultiple accounts may be a sign of suspicious abnormal behavior. Otherconditions may be based on usage of the account.

Another data source may include billing information such as the numberof credit cards on the account, the number of accounts that use aparticular credit card, number of names used on credit cards of anaccount, number or frequency of changes to billing information, countryof IP address matched against credit card country, geographic regiondiversity of billing address, and other billing related information. Thebilling data source may be from a billing system of the communicationplatform. Outside data sources may additionally or alternatively beused. For example a data source with stolen or flagged credit cardinformation can be used.

Yet another data source can include endpoints of an account. Patterns inendpoints may relate to the variety of owned or used endpoints by anaccount, variety of endpoints of incoming communication, variety ofendpoints in outgoing communication, number or percentage ofcommunications that are international, types of endpoints (e.g., shortcodes, mobile numbers, landlines, business numbers, etc.)

In the variation where the communication platform is a communicationapplication platform, the application configuration can be another datasource used in fraud rule conditions. Preferably, an applicationparameter is set within an account to reference the application resource(e.g., a document with the communication instructions). The applicationparameter is preferably a URI string that points to an applicationserver of the account holder. The number of times the URI is used indifferent accounts may be the basis of a fraud rule condition. Theapplication parameter may alternatively be a binary data file orexecutable code, and the raw application resource can be compared toother. For example, a cryptographic hash or fingerprint may be generatedand used in comparing applications across accounts or sub-accounts.While static application configuration may be used, applications may beable to redirect application state control to other URIs and thus thefraud rule condition may be based on the URIs that are used throughoutthe processing of a communication session.

Similar to the fraud rules based on application configuration, mediaresource usage can additionally be used. If two or more accounts orsub-accounts, are using the same media resources, then those may beassumed to be operated by the same entity.

In addition to the data source, the time period in which the pattern isdetected, age of the account, number of accounts, percentage of usagethat is not flagged as suspicious and other qualifying conditions mayprovide additional context to the data source conditions.

The fraud scoring system 120 is communicatively coupled to theoperational components 130 of the communication platform 100. Theoperational components 130 of the communication platform can include anyservers, databases, processors or other resources that either defineaccount configuration, account usage, or other aspects of the accountwithin the platform. Preferably, the operational components include acall router that processes communication. In particular, the call routercontrols and facilitates the execution of a telephony application duringa communication session. The various operational components 130 mayadditionally be used in enforcing some response to detection of illicitbehavior by an account or sub-account.

2. Method for Preventing Illicit Use of a Communication Platform

As shown in FIG. 2, a method for preventing illicit use of acommunication platform in accordance with a preferred embodiment mayinclude enrolling a plurality of accounts in a telecommunicationsplatform block S110, at a fraud scoring system, receiving usage data ofa telephony platform component block S120, calculating a fraud scorefrom the usage data block S130, detecting when fraud scores of anaccount satisfy a fraud threshold block S140, and taking action when afraud score satisfies a fraud threshold block S150. The method functionsto enable heuristic based identification and prevention of telephonyfraud. The method is preferably used to prevent illicit use cases invoice or video calls, short message service (SMS) messages, multimediamessaging service (MMS) messages, Fax, or any suitable form of telephonycommunication. The method can additionally be applied to IP basedcommunication or proprietary communication channels such as SIP, Videoconferencing, screen sharing or other suitable communication mediums.The method is preferably performed by a fraud scoring system which is apreferably a sub-component of telephony application platform such as thetelephony platform described in U.S. patent application Ser. No.12/417,630, filed 2 Apr. 2009 and titled “System and Method forProcessing Telephony Sessions”, which is incorporated in its entirety bythis reference. Integration into a telephony platform preferably enablesthe gathering of usage data from a plurality of various telephonyplatform components. The telephony platform components are preferablythose components that facilitate calls or messaging such as calldatabases or SMS databases, but may alternatively include componentsfacilitating telephony application setup or operation such as account orcredit card databases. The telephony platform is preferably amultitenant platform with multiple user accounts and optionallysub-accounts that independently use the platform. The telephony platformcan be a self-sign up service, and the programmatic interface into thetelephony platform can make it appear more appealing for illicit use.Entities can be freed of the hassle and complexity of arranginglong-term contracts or other agreements that normally act as a barrierto telephony based fraud. The method is preferably applicable topreventing toll fraud in a telephony platform but may additionally oralternatively be used to prevent terms of service violations, denial ofservice attacks on a telephony platform or an outside system, suspiciousbehavior, credit card fraud, phishing attacks, and/or any suitable typeof illicit use of a telephony platform.

The method is preferably capable of addressing internal telephony fraud(i.e., fraud performed by account holders on the telephony platform)and/or external telephony fraud (i.e., fraud attempts originating onoutside systems but occurring through the telephony platform). Themethod is preferably capable of detecting coordinated illicit behaviorperformed across two or more accounts of the platform. Additionally oralternatively, the illicit behavior of a single account can additionallybe addressed. The method preferably uses a heuristic based approachusing rules defined in a rule set of the fraud scoring system. Rulesused in the method can preferably be crafted and maintained by fraudanalysts, which functions to enable analysts to use their unique insightinto fraud scenarios to automatically detect future scenarios using thefraud scoring system. The method additionally can automate the detectionand actions taken by fraud analysts for a system. The method mayadditionally include Bayesian learning, neural networks, reinforcementlearning, cluster analysis or any suitable machine learning oralgorithmic approaches to facilitate identifying illicit use cases.Preferably a combination of automatic fraud rule generation and fraudanalyst input is used in during the method of the fraud scoring system.The method is preferably capable of identifying a wide variety ofillicit use cases as defined in the rule set. When illicit use of thetelephony platform is matches a rule, the fraud scoring systempreferably acts to prevent that instance of illicit use from continuing.

Block S110, which includes enrolling a plurality of accounts in atelecommunications platform, functions to setup, configure, andinstantiate multiple entities within the platform. An account within thetelephony platform preferably has a unique identifier or uniquelyidentifying characteristics. Fraud detection is preferably detectedwithin individual accounts or through two or more accounts that shareusage data patterns (which often indicate a single entity iscoordinating both accounts to distribute the signals of illicit behavioracross multiple accounts). Enrolling an account may be initiated by auser through a user interface, but an account and/or a sub-account mayalternatively be configured programmatically through an API such as aREST API of the platform. The enrollment may additionally include withinone account, enrolling at least one sub-account that is managed by thefirst account. The sub-account (i.e., the child account) will often bean end customer of a service of the primary/parent account holder. Forexample, a customer care application may create a parent account, andwithin that account each end-customer is given a sub-account so thatusage, data, and configuration can be independently managed. The parentaccount holder preferably manages these accounts. Sub-accounts arepreferably created and managed through an API. The method can beparticularly useful for systems that use sub-accounts in that,individual sub-accounts may be performing illicit behavior and theaccount holder may not have sufficient data when operating on top of theplatform to detect the illicit behavior. The fraud detection service canbe a beneficial service in promoting app developers to build on top of aplatform.

Basic configuration of an account preferably occurs during enrollmentbut can be completed at a later time. Enrolling an account preferablyincludes an enrolling-account assigning at least one communicationendpoint address to the account. Preferably, at least one phone numberis associated with an account. Multiple phone numbers can additionallybe configured. The communication endpoint may alternatively be a SIPaddress, email address, username, or any suitable address identifierused in routing communication to a destination. An assigned endpoint maybe purchased/selected from the platform, ported from an existing system,or added to the account in any suitable manner.

The enrolling account additionally configures application resources.Preferably, an endpoint will be mapped to an application URI, which willbe an external, internet-accessible resource that provides communicationinstructions for a communication session. Multiple application URI's mayadditionally be configured for different communication states or events.For example, there may be a primary application URI for incoming calls,an outgoing application URI that takes control of outgoing communicationsessions, a fallback application may be used for when errors occur,there may be different application URIs for different mediums (e.g.,voice, video, SMS, MMS, fax, eats.), different application URIs fordifferent regions or originating endpoints. Each endpoint assigned to anaccount can additionally be uniquely configured. The configuredapplication resources may alternatively or additionally include mediafiles used in an application such as an application executable binary,instruction file, playable audio or video, or other suitable mediaresources.

The enrolling account may additionally configure billing information.The billing information will preferably include at least one creditcard, but may alternatively be any suitable payment mechanism such as abank account, links to an outside account with credit/points. Thepayment mechanism information will preferably include an accountidentifier (e.g., a credit card number), billing name, billing address.Multiple payment mechanisms may be setup.

Block S120, which recites at a fraud score system receiving usage dataof a telephony platform component, functions to collect data used tocalculate a fraud score. The usage data is preferably data collected andmaintained independently from the fraud score system. The usage datathus typically reflects operational metrics of a telephony platform. Forexample, a call history database may store records of when calls wheremade and what the destination endpoints were for those calls. In thisexample, the primary purpose of the call history database may be foranalytics but the data may additionally be used for calculating a fraudscore. Alternatively, usage data may be collected with the explicitintent to measure data pertinent to calculating a fraud score. The fraudscoring system is preferably coupled through a network to a telephonyplatform component. More preferably the fraud scoring system is coupledthrough a network to a plurality of telephony platform components asshown in FIG. 3. A telephony platform component is preferably a machinethat provides the usage data. The telephony platform components coupledto the fraud scoring system may include call history databases,messaging history databases, account databases, credit card hashdatabases, account databases, client device information databases, IPaddress databases, phone number databases, credit card or spendingdatabases, API logs, and/or any suitable machine containing data usefulfor calculating a fraud score. The fraud scoring system is preferablyconfigured to actively initiate communication with the telephonyplatform components, and the platform components preferably respond withany requested usage data. Alternatively, the coupled machines mayindependently send usage data to the fraud scoring system through asubscription or push-based service.

The fraud scoring system preferably refreshes usage data periodically.For example, fraud score system may receive new usage data from at leasta subset of machines every half hour. In another variation, telephonyplatform components may send usage data continuously, when new data iscollected, or for any suitable reason. In yet another variation, a fraudscoring system may be integrated into a data stream. In this variationdata would preferably not need to be replicated or sent through aseparate fraud scoring system. A fraud scoring system can preferablysubscribe to designated data streams as shown in FIG. 4 but mayalternatively be integrated into a data stream in any suitable manner.The fraud scoring system may additionally poll or actively requestupdate usage data from components. Additionally or alternatively, avariation of a method of a preferred embodiment may include updatingreceived usage data upon receiving a trigger signal Block S122 as shownin FIG. 5, which functions to enable fraud checking programmatically. Inresponse to a trigger signal, the fraud scoring system preferablyactively initiates the transmission of usage data from a telephonyplatform component to the fraud scoring system. The trigger signal ispreferably an instruction associated with an application programminginterface (API) call. The API call preferably causes usage data to beupdated, a fraud score to be calculated, and action to be taken ifappropriate. The API call may alternatively trigger a subset of theabove steps. A telephony platform is preferably configured to send anAPI call to update the fraud scoring system when events occur that havea high correlation to fraud. For example, an API call to update thefraud scoring system may be sent before, while, or during updating anaccount, performing a credit card transaction, detecting high accountconcurrency, or during any suitable event. A fraud score API mayadditionally be used to perform other interactions with the fraudscoring system. For example, a fraud score API may trigger any suitablesteps of the fraud scoring method; may create, edit, delete, orotherwise augment fraud rules, usage data, usage scores, fraud actions,or other parameters of the fraud scoring system; and/or interact withthe fraud scoring system in any suitable way.

Block S130, which recites calculating a fraud score from the usage data,functions to process usage data to generate a metric that reflects thelikelihood that illicit use of the telephony platform is occurring.Fraud scores are preferably calculated for a set of fraud rules. The setof fraud rules are used to calculate a set of fraud scores (e.g.,measure or indicators of fraud). Additionally, fraud thresholds candefine when particular types of actions are taken. A fraud rulepreferably includes a usage condition, a usage data time window, and anaccount age condition. The fraud rules may additionally be conditionswithin a single account or pattern conditions across multiple accounts.The usage conditions are particular patterns in usage data (e.g.,account configuration or communication history). The usage conditionsare preferably particular patterns such as some threshold on the numberor percentage of events or resources that would trigger activating thefraud rule (e.g., assigning the defined fraud score for that rule). Theusage condition can additionally specify conditions found acrossmultiple accounts. For example, a usage condition may be foridentical/corresponding billing information configured in more thanthree accounts. The usage data time window is the window that is used todefine what data is analyzed. Some exemplary time windows could includethe past 24 hours, the past week, the past month, the past year, oracross all data (e.g., no time window). The account age condition maydefine for how long the rule is monitored for an account. Some illicituse scenarios may only be seen with new accounts. For example, theaccount age condition may configure a fraud rule to apply to an accountfor the first week after the account is created. If the conditions ofthe fraud rule are satisfied a defined score is preferably assigned.These fraud scores are preferably stored per account. If the fraud ruleis defined for condition patterns across multiple accounts, the fraudscore is preferably assigned to each account. The fraud score ispreferably a numeric value but may alternatively be a label or anysuitable construct to communicate fraud likelihood. In this document wetreat high fraud scores as indicating a greater likelihood of illicituse, but any suitable relationship may be defined. A fraud score ispreferably associated with at least one key/identifier. The key may bean account, sub-account, an endpoint (e.g., a phone number), a creditcard hash, or any suitable key. A plurality of fraud scores (e.g., oneper fraud rule) is preferably calculated to monitor various entities andapproaches to performing fraud in a telephony platform. For example, aseries of fraud scores may be calculated to monitor accounts for oneform of telephone fraud, while another series of fraud scores may becalculated to monitor credit card abuse across accounts. The fraud scoreis preferably indicative of activity during a specified time window, butmay alternatively be an aggregate value (preferably factoring in olderfraud scores to reflect multiple time windows). Calculation of fraudscores may additionally involve creating associations between subsets ofthe received usage data. Associations can be made based on useraccounts, credit cards used to pay for accounts, endpoints or endpointprefixes, source or destination carriers, and/or any suitable parameterthat can be used to associate various data points in the usage data.

As described, fraud scores are preferably calculated to generate metricsthat reflect the likelihood of fraud. These metrics may be associatedwith various parameters or combination of parameters of a telephonyplatform. Block S130 preferably includes calculating a fraud score fromusage data associated with call history data Block S132, calculating afraud score from usage data associated with messaging history data S134,and/or calculating a fraud score from usage data associated withplatform account configuration data S136, but any suitable usage datamay alternatively be used in calculating fraud score. Correspondingly,the block S130 preferably includes at least one fraud rule of the set offraud rules including identifying communication-applicationconfiguration shared between at least two accounts, identifying sharedpatterns of media resource usage in two accounts, detecting sharedbilling information across two or more accounts, detecting communicationhistory patterns across at least two accounts, and other suitable fraudrule conditions that are defined for patterns in usage data betweenmultiple accounts.

Block S132, which recites calculating a fraud score from usage dataassociated with call history data, functions to create a fraud scorebased on patterns in calls occurring on the telephony platform. Severaldifferent parameters of a call may have been measured and included inthe usage data. For example, call duration, account(s) associated with acall, call destination endpoints, caller endpoints, carrier origin of acall, destination carrier, frequency of calls, number of concurrentcalls for an account, or any suitable parameter of call data. Such callrelated usage data can preferably be used to calculate fraud scoresbased on various heuristics. In one variation, high call concurrency(i.e., multiple calls occurring on the telephony platformsimultaneously) for a new account is indicative of illicit use of thetelephony platform. A fraud score that reflects this is preferablycalculated from such data. In this variation, the fraud score preferablyhas a direct relationship to concurrency and an inverse relationship tothe age of the account. In another variation, numerous call endpointsmatching designated prefix patterns may additionally be an indicator ofillicit use. A fraud score that reflects this is preferably calculated.Preferably, a fraud rule is defined for each communication historycondition or set of conditions. Additionally, audio or video of a callmay be used in calculating a fraud score. For example, white noiseanalysis of a call may be included in or extracted from usage data.White noise analysis may enable the fraud scoring system to detect if aphone call had anyone on either side of a call. In this example, a longsilent phone call may be associated with illicit use of the telephonyplatform, and the white noise detection could be used to calculate afraud score that reflects this heuristic.

Block S134, which recites calculating a fraud score from usage dataassociated with messaging history data, functions to create a fraudscore based on patterns in messages occurring on the telephony platform.Messaging history data may include any data related to SMS, MMS, orother suitable messages communicated through the telephony platform.Calculation of a fraud score may include the use of usage data analogousto the usage data described above for call data, such as messageendpoints, account(s) associated with a message, message frequency,message frequency as a factor of account age, carrier origin of amessage, carrier destination of a message, or any suitable parameter ofa message or messages sent through the telephony platform. Messagecontent and message conversations conveyed in usage data of the messagesmay additionally be used to calculate a fraud score. In one variation,messages replying to account messages that instruct the sender to stopsending messages (e.g., a message with the message ‘STOP’) preferablycontribute towards a higher fraud score. Accounts that receive a higherpercentage of stop-messages are more likely to be practicing behaviorthat is undesirable to users. In an alternative variation, if a largenumber of spam-like text messages are delivered to endpoints matching aprefix and no stop-messages are received, this may also be an indicatorof illicit behavior (e.g., a nefarious user may be trying to terminateas many text messages to a particular carrier).

Block S136, which recites calculating a fraud score from usage dataassociated with platform account configuration data, functions to usemetrics collected from the telephony platform that do not directlyrelate to voice, video or messaging. Usage data associated with platformaccount configuration data may include information pertaining to useraccounts, credit cards, endpoints, client devices, telephony applicationURI's, or any suitable platform account data. The configuration datapreferably includes communication-application configuration, whichincludes variables and resources used in customizing and defining theapplication(s) of the account. One fraud rule may be defined for acondition of identifying communication-application configuration sharedbetween at least two accounts. If multiple accounts have the sameapplication configuration, then this can be used as a signal that thetwo accounts are used for the same task. Outside entities may set upmultiple accounts to perform the same task to avoid detection, butidentical application configuration can be a signal that the accountsare managed by the same entity or two cooperating entities. Preferably,applications are defined by application URIs that are associatedwith/mapped to communication endpoints. String comparisons of the URIscan be performed to identify matching applications used in multipleaccounts. In some situations, some application URI's may be whitelistedso that they can be used in multiple accounts. In a similar, variationthe actual application media resources consumed during execution of anapplication can be used to indicate similar functionality. Acommunication platform may transfer application state to variousapplication URIs during a communication session. These application URIscan be similarly tracked and compared. Also media such as theinstruction documents (telephony instructions in an XML document), audiofiles, video files, and other resources can be fingerprinted orotherwise processed to create an identifier that can be used to detectsimilar or identical media resources. Fingerprinting data preferablyincludes creating an identifier of the content of the media file. Thefingerprint identifier can be preferably easily compared to otherfingerprint identifiers in other accounts to determine if identical orsubstantially similar media is used. A fingerprint identifier preferablyfunctions so that media can be matched despite variations in theencoding of the content. For example two images of the same picture butof slightly different dimensions and size ratios can be shown to bematching. Alternatively, the raw file may be compared. Media resourceusage during communication sessions can also be used as signals ofillicit behavior. For example, an image sent over MMS by one account maybe fingerprinted. A second account additionally sends an image of MMSand the image is similarly fingerprinted. The fingerprint identifiersare then compared, and if they indicate the image content matches, thismay trigger a fraud rule around two accounts sending identical imagesover MMS. Media fingerprinting can similarly be applied to audio, videoand other suitable media mediums.

In one variation, calculating a fraud score from usage data associatedwith credit card data preferably involves comparing hashes of creditcard numbers. By comparing billing information within and acrossaccounts, the fraud scoring system functions to check diversity ofpayment mechanism. Payment mechanisms are preferably not shared acrossnumerous accounts. This can be a signal that one entity is setting upmultiple accounts for some reason. Within an account the paymentmechanisms preferably have little diversity. If several credit cardswith multiple names and addresses may be a sign that stolen credit cardsare being used. As an example, a plurality of new accounts created andset up using the same credit card may be an indicator of illicit use.Credit card hash records for new accounts are preferably compared toidentify credit cards used multiple times. In this variation, a creditcard used multiple times for different accounts would preferablycontribute to a higher fraud score. Similarly, many telephonyapplications allow accounts to set up an application to handle calls ormessages by specifying a URI. In one variation, if one URI is configuredfor a plurality of new accounts, then this may indicate illicit use asit indicates one entity is setting up multiple accounts for the samepurpose.

Block S140, which recites detecting when fraud scores of an accountsatisfy a fraud threshold, function to monitor and assess when ascenario of illicit behavior is occurring based on the fraud scores.Block S140 preferably includes storing/recording the fraud score. Asdescribed above, the fraud scores are preferably indicative of a fraudscore for a particular time window, but may alternatively be anaggregate metric. The fraud scores are preferably stored such that anassociated account, endpoint, application, and/or any suitable key maybe referenced when retrieving data. In one variation block storing ofthe fraud scores is optional, and assessment can be performed directlyafter calculating fraud scores, without persistently storing fraudscores. Preferably, the same set of fraud rules are used in calculatingfraud scores across all the accounts/sub-accounts. Fraud thresholds candefine when particular types of actions are taken. In oneimplementation, the fraud scores associated with an account orsub-account are preferably summed, and if the total fraud score is abovea define fraud score threshold a response is made in block S150.Additionally, there may be different levels of fraud thresholds. Forexample a fraud threshold may be defined for fraud scores from 20-50, asecond fraud threshold for 51-75, and a third fraud threshold for scoresover 76. These three fraud thresholds can define three levels of actionstaken in block S150. The fraud reaction can alternatively be based onthe fraud scores of a particular fraud rules. For example, specificfraud rules (when satisfied or for certain scores) may define a reactionof flagging an account or throttling an account, while some fraud rulesmay define more severe illicit behavior and can initiate automatictermination of the account.

Block S150, which recites taking action when a fraud score satisfies afraud threshold, functions to react to fraud scores that indicateillicit behavior. The reaction to a fraud score may include flagging theaccount, throttling communication of an account, requesting additionalbilling information, notifying account holder, notifying an analyst ofthe communication platform, performing additional fraud detectionanalysis on the account, blocking particular actions on the account, orperforming any suitable action. In a sub-account variation, the parentaccount of a sub-account is preferably notified of the sub-accountillicit behavior. The notification can be an email notification, amessage within the communication platform web platform, or notificationmade through the API of the communication platform. Account holders mayhave multiple sub-accounts using their service provided on top of thecommunication platform. By performing the fraud regulation bysub-accounts, the communication platform can avoid taking action againstthe account itself since many sub-accounts may be using thecommunication platform in a proper manner. This functions to simplifyand abstract the fraud prevention aspect away from account holders suchthat the communication platform can handle illicit use detection. Afraud scoring system preferably includes a set of fraud rules (i.e., arule set) stored using any suitable schema. The rule set preferablyenables various heuristics to be configured and/or updated to keepcurrent with the latest fraud attempts. Fraud score patterns may includethresholds for a particular fraud score or alternatively a group offraud scores. Some exemplary fraud score patterns may include takingaction when there are more than a specified number of internationalcalls lasting longer than a specified amount of time, when an averagelength of international calls is greater than a specified amount oftime, when greater than a specified number of outbound SMS messages to aclassification of prefixes (e.g., UK prefixes) are made, when more thana specified number of unique credit cards are added to an account, whenthe credit cards of an account use more than a specified number of zipcodes, when one credit card is used on more than a specified number ofaccounts, when one IP address is used across more than a specifiednumber of accounts, when the account balance is more than a specifiedamount for an account and the age of the account is less than aspecified number of days, when the answer rate of outbound calls is lessthan a specified percentage and/or when any suitable pattern issatisfied, As shown in FIG. 9, rule sets may be dependent on measuredmetrics in combination with a threshold, time period for the metrics,and account age. Alternatively, any suitable parameters may be specifiedto determine a rule set. Fraud score patterns may alternatively betrending patterns from a time series of related fraud scores. Fraudreactions preferably include suspending an account, blacklisting creditcard numbers, blacklisting application URI's or IP's, rate-limitingservices provided to an offending account, remove or adjust servicesprovided to an offending account (e.g., remove international services),flag the account for a human fraud analyst to investigate, and/or anysuitable course of action. The fraud reaction is preferably signaled tothe telephony platform, and the resulting reaction preferably altersbehavior of the telephony platform to prevent a suspected case ofillicit use of the platform. There may additionally be different levelof responses based on the severity of the fraud score, and fraudreactions may be applied in stages if the fraud score does not subside.

Additionally or alternatively, a method of a preferred embodiment mayinclude generating a fraud rule block S160 as shown in FIG. 10, whichfunctions to produce a fraud score based on collected data. In onevariation, a fraud score set is preferably predominately generated byfraud analysts. This preferably enables fraud analysts to apply uniqueinsight into fraud attempts to enable automatic detection. In avariation that implements block S150, at least a subset of the fraudrule set is generated through analysis of the data. As mention aboveBayesian learning, neural networks, reinforcement learning, clusteranalysis or any suitable machine learning techniques may be used toextract rules to identify fraud scenarios. The generating of a fraudrule may be active or reactive. Active generation of a fraud rule willpreferably automatically generate a rule based on observed data.Reactive fraud rule generation preferably generates a fraud rule after afraud scenario has happened. Data from the time of the fraud canpreferably be replayed such that a fraud rule may be generated thatwould have set the fraud score to reflect the occurrence of the fraudscenario.

An alternative embodiment preferably implements the above methods in acomputer-readable medium storing computer-readable instructions. Theinstructions are preferably executed by computer-executable componentspreferably integrated with a fraud scoring system. The fraud scoringsystem preferably includes a fraud rule set and a fraud scoring API. Thefraud scoring system is preferably integrated into a telephony platformcapable of facilitating voice, video, or message communication. Thecomputer-readable medium may be stored on any suitable computer readablemedia such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD orDVD), hard drives, floppy drives, or any suitable device. Thecomputer-executable component is preferably a processor but theinstructions may alternatively or additionally be executed by anysuitable dedicated hardware device.

As a person skilled in the art will recognize from the previous detaileddescription and from the figures and claims, modifications and changescan be made to the preferred embodiments of the invention withoutdeparting from the scope of this invention defined in the followingclaims.

What is claimed is:
 1. A method comprising: enrolling a plurality ofaccounts on a telecommunications platform, wherein an account includesaccount configuration; at a fraud detection system of thetelecommunications platform, receiving account usage data, wherein theaccount usage data includes at least communication configuration dataand billing configuration data of account configuration and furtherincludes communication history of the plurality of accounts; calculatingfraud scores of a set of fraud rules from the usage data, wherein atleast a sub-set of the fraud rules include conditions of usage datapatterns between at least two accounts; detecting when the fraud scoresof an account satisfy a fraud threshold; initiating an action responsewhen a fraud score satisfies the fraud threshold.
 2. The method of claim1, wherein communication configuration includescommunication-application configuration; wherein at least one fraud ruleof the sub-set of fraud rules comprises identifyingcommunication-application configuration shared between at least twoaccounts.
 3. The method of claim 2, wherein thecommunication-application configuration is an application URI string. 4.The method of claim 1, wherein the communication history includes mediaresource usage; and wherein at least one fraud rule of the sub-set offraud rules comprises identifying shared patterns of media resourceusage in two accounts.
 5. The method of claim 1, wherein at least onefraud rule of the sub-set of fraud rules comprises detecting sharedbilling information across three or more accounts.
 6. The method ofclaim 5, wherein the shared billing information can include a sharedcredit card or shared billing address.
 7. The method of claim 1, whereina fraud rule includes at least one usage pattern condition; and wherecalculating a fraud rule comprises assigning a defined score if theconditions of the fraud rule are satisfied; and wherein detecting whenthe fraud scores of an account satisfy a fraud threshold comprisesadding fraud scores of the set of fraud rules.
 8. The method of claim 7,wherein a fraud rule includes a usage data time window, and an accountage condition.
 9. The method of claim 1, further comprisingautomatically generating a fraud rule through usage data anomalydetection; and adding the fraud score to the set of fraud scores. 10.The method of claim 1, wherein initiating an action response includesflagging the associated account; and further comprising providing ananalyst interface wherein an analyst can modify the set of fraud rulesand modify flagged accounts.
 11. The method of claim 1, furthercomprising a second sub-set of fraud rules that include conditions ofusage data patterns within the account.
 12. The method of claim 1,wherein the plurality of accounts include accounts and sub-accounts.